Current Notes concerning the "Getting Started" book:
# ORIGINAL: 3dt2.1/examples/schemers/readme.txt
====================================================

----------------------------------------^M
INFORMATION ABOUT THE SAMPLE SCHEME CODE
----------------------------------------
^M
---------^M
CHAPTER 1^M
---------^M

1) Scheme procedures that enable you to generate the "challenge" solids
   pictured in Figures 1-12 through 1-17 on pages 1-27 through 1-34 are
   provided in the file  egsolids.scm  on the Getting Started disk.

   Before loading this file, you must load the file  viewer.scm,  which
   is also provided on the Getting Started disk.
^M
2) The following files have been modified to work with the latest version^M
   of the 3D Toolkit:^M
^M
     castle.scm^M
     egsolids.scm^M
     flight.scm^M
     viewer.scm^M
^M
3) The following utility files have been modified to work with the latest^M
   version of the 3D Toolkit:^M
^M
     consts.scm^M
     objects.scm^M
     rdrpoint.scm^M
^M
^M
---------^M
CHAPTER 4^M
---------^M

1) Scheme procedures that solve the basic tasks outlined in Chapter 4 are
   provided in the following files, which have been modified to work with^M
   the latest version of the 3D Toolkit:

     DICE             dice.scm
     BENDING WIRES    bendwire.scm
     RUBBER BANDING   rbprocs.scm

   Provide your own extensions to these projects.^M
^M
2) The following utility file has been modified to work with the latest^M
   version of the 3D Toolkit:^M
^M
     std-view.scm^M

^M
----------------------^M
OTHER CODE INFORMATION^M
----------------------^M
^M
1) The remaining sample Scheme code on the Getting Started disk is
   provided so that you can run it while you are reading the book. The files,
   and the sections with which they are primarily associated, are:

     rdrpaint.scm     Everywhere (this includes basic coloring and rendering
                      procedures)
     consts.scm       Everywhere (this includes some important constants in
                      case your initialization process does not include
                      loading  acis.scm)
     castle.scm       Chapter 1: "A Castle Tour", "Return To The Castle"
     flight.scm       Chapter 1: "A Castle Tour", "Return To The Castle"
     viewer.scm       Chapter 1: "Where Am I?" and beyond
     std-view.scm     Chapter 2: "Decisions, Decisions",
                      Chapter 3: "Solid Bodies" and beyond
     report.scm       Chapter 3: "Parts and Filters"
     objects.scm      Everywhere and Chapter 3: "Flying"

^M
^M
----------------------------------------------------------
USING THE "GETTING STARTED" BOOK WITH ACIS 3D TOOLKIT v1.2
----------------------------------------------------------
^M
^M
---------^M
CHAPTER 2^M
---------^M
^M
1) The linear-edge procedure generates an error message if you provide two^M
   equal arguments to the procedure. In consequence, the "wireframe" and ^M
   the "yellow road" procedures developed on pages 2-46 through 2-54 work^M
   as described only when you provide different arguments for the two^M
   positions that differ in their components.  For example, the wireframe^M
   box does NOT degenerate to a rectangle, line segment, or point.^M
^M
   To make these procedures work in more general situations, you need to^M
   develop a "smart-linear-edge" procedure that does something in the^M
   zero-length case, and then use it in place of the linear-edge^M
   procedure. For more information, examine the relevant code in the^M
   viewer.scm  file to see how Spatial handles this situation.^M
^M
^M
---------^M
CHAPTER 3^M
---------^M
^M
1) In the 3D Toolkit v1.2, when you highlight a face using^M
   entity:set-highlight, only the edges that delimit the face are^M
   highlighted. Therefore, the predicate  entity:highlighted?  always^M
   yields a result of  #f  when applied to a face, even if you have^M
   just highlighted that face. Furthermore, if you check the edges with^M
   entity:highlighted?, you will find that they are highlighted, even^M
   though you haven't highlighted them. Apart from this unexpected^M
   behavior, the description of highlighting on pages 3-18 and following^M
   is accurate.^M

2) On pages 3-73 through 3-75,^M 
   change:    part:set-active^M 
   to:        env:set_active-part^M
^M
3) On pages 3-73 through 3-74,^M
   change:    part_active^M
   to:        env_active-part^M
^M
4) On pages 3-73 through 3-74,^M
   change:    part 0^M
   to:        part 1^M
^M
5) On page 3-76,^M
   eliminate: part:add-entity^M
   A similar procedure does not exist.^M
^M
6) On page 3-76,^M
   change:    part_count^M
   to:        env_count-parts^M
^M
7) The functionalities of  wcs:to-wcs-transform  and^M 
   wcs:to-model-transform  described on pages 3-84 and 3-85 are the^M
   reverse of what they were in the previous release of the ACIS 3D^M
   Toolkit. Exchange these two names wherever they appear so that^M
   the sample code works as described.

^M
---------^M
CHAPTER 4^M
---------^M
^M
1) On pages 4-15, 4-16, and 4-17^M
   change:    rb:line^M
   to:        rbd:line^M
^M
   rbd:line did not work as expected because the previous ON/OFF flag^M
   pushed and popped the driver from the driver stack. Now, rbd:line ^M
   creates and returns a line rubberband driver. The ON/OFF flag now^M
   indicates if the driver is pushed onto the stack when it is created.^M
^M
   To make the examples work,^M 
   change:    (rb:line OFF)^M
   to:        (rbd:clear)^M
^M
2) On pages 4-17 through 4-20,^M
   change:    rb:scheme^M
   to:        rbd:scheme^M
^M
   In addition, the following have been eliminated:^M
              rb-init-hook^M
              rb-start-hook^M
              rb-update-hook^M
              rb-repaint-hook^M
              rb-stop-hook^M
              rb-end-hook^M
^M
   For more information, refer to rbd:scheme.^M
^M
   The global variables for rubberbanding have been eliminated, and the^M
   operation of rbd:scheme has changed dramatically. The new operation ^M
   is much more flexible. Refer to the 3D Toolkit documentation and^M
   and examples. The examples, as shown in the book, do not work.^M
^M

;;; end of file  readme.txt

